chore(deps-dev): bump @types/node from 22.19.17 to 24.13.3 - #296

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Test Coverage Report

Leaving this open. The bump itself is green and type-only, but it needs to land on our internal source-of-truth repo first — this repository is a per-release mirror, so a dependency change applied only here either blocks the next release snapshot or gets regenerated away by it.

One thing worth doing deliberately rather than automatically when we take it: @types/node 24 types against a Node 24 runtime, while package.json engines still admit ^20.19.0 || ^22.13.0. Bumping the types ahead of the minimum supported runtime can surface APIs that don't exist on Node 20, and the type checker won't complain. So this goes in alongside a look at the engines range, not before it.

Queued internally.

Holding this one deliberately — not because anything here is wrong, but because it would put our type layer a runtime ahead of anything we actually test.

package.json declares "node": "^20.19.0 || ^22.13.0 || >=24", but .github/workflows/ci.yml runs matrix.node-version: [20, 22] for both Unit Tests and Build. We claim to support Node 24 and never execute a single line on it. Moving @types/node to 24 means TypeScript starts accepting Node 24-only APIs while our declared floor is still 20.19 and nothing in CI would notice — the failure would surface as a runtime crash on a supported version, not as a red check.

That is a gap worth closing in the other order: add Node 24 to the Unit Tests and Build matrices first, then take this bump. I'll open that separately.

Nothing to do on your side, dependabot — this will be picked up again once the matrix covers 24.